fix(NODE-6173): add rangeV2 feature flag toggle to Node.js bindings #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is changing?
See the ticket for motivation/why it would be convenient to have this earlier than the 'main' range V2 work 🙂
Is there new documentation needed for these changes?
No
What is the motivation for this change?
Testing
Porting change from: mongodb/libmongocrypt#809
Release Highlight
Adds an internal flag to enable
rangeV2A new option
rangeV2can be passed to the MongoCrypt constructor to enable the new protocol. It is marked expiremental because it will likely be removed in a future release, this is for testing only.Double check the following
npm run check:lintscripttype(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript